…ository Rule Suites (Insights) (#461)

## Description

This pull request introduces several changes across multiple files to
enhance the functionality and structure of GitHub-related classes in the
codebase. The most notable updates include replacing `HostName` with
`GitHubContext` for improved context management, restructuring
properties in `GitHubOwner` subclasses, and updating XML format
definitions to reflect the new structure.

- Fixes #454

### Context Management Updates:
* Replaced the `HostName` parameter with `GitHubContext` in constructors
across multiple classes (`GitHubAppInstallation`, `GitHubArtifact`,
`GitHubEnvironment`, `GitHubOrganization`). This change centralizes
context-related properties, such as `HostName`, for better scalability
and readability.

### GitHubOwner Class Restructuring:
* Removed redundant properties (e.g., `Company`, `Blog`, `Plan`) from
the `GitHubOwner` class and its subclasses (`GitHubEnterprise`,
`GitHubOrganization`, `GitHubUser`). Added new properties such as
`Description` and `Website` to better align with GraphQL schema
mappings.

### GraphQL Mapping Enhancements:
* Introduced static `$PropertyToGraphQLMap` hashtables in
`GitHubEnterprise` and `GitHubOrganization` classes to define mappings
between class properties and GraphQL fields, improving maintainability
and integration with GraphQL APIs.

### XML Format Updates:
* Updated the `GitHubOwner.Format.ps1xml` file to include new properties
(`DisplayName`, `CreatedAt`) in table views for improved visualization
of `GitHubOwner` objects. Removed deprecated columns such as `Company`
and `Plan`.

## Type of change

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [ ] 📖 [Docs]
- [ ] 🪲 [Fix]
- [x] 🩹 [Patch]
- [ ] ⚠️ [Security fix]
- [ ] 🚀 [Feature]
- [ ] 🌟 [Breaking change]

## Checklist

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas

- Created TEMPLATE.ps1 for Pester testing framework setup.
- Added Teams.Tests.ps1 to test GitHub Teams API functionalities.
- Introduced Users.Tests.ps1 for user-related API tests.
- Developed Variables.Tests.ps1 to manage GitHub repository variables.
- Each test script includes setup and teardown logic for authentication and resource cleanup.
- Implemented various test cases for creating, updating, retrieving, and deleting GitHub resources.

…zation

…Install-GitHubAppOnEnterpriseOrganization function; remove obsolete tests from Organizations.Tests

… of Organizations.Tests

… wildcard matching and add -WhatIf parameter for safety

…ubOrganization function

…y parameters for organization name and owners; improve debug logging in process block

…ion's begin block

…g organization details before removal; improve organization retrieval in tests

… parameter for organization retrieval in enterprise context; ensure accurate logging of organizations

…e unnecessary enterprise parameter and cleanup calls

… parameter for organization retrieval in enterprise context

…xt using Invoke-GitHubAPI

…or enterprise context

…g unnecessary logging and directly removing organizations for enterprise context

…-GitHubOrganization function

…r enterprise cleanup

…ubOrganization

…d add tests for app installation and organization updates

…s test suite

…t information

…xceptions for non-enterprise installations

- Created TEMPLATE.ps1 for standardized test structure.
- Implemented Teams.Tests.ps1 to validate GitHub Teams functionality, including team creation, retrieval, updating, and deletion.
- Developed Users.Tests.ps1 to test user-related API calls, including user retrieval and updates.
- Added Variables.Tests.ps1 to cover GitHub variable management, including setting, updating, and removing variables for users and organizations.
- Each test file includes setup and teardown logic to ensure a clean testing environment.
- Utilized Pester's logging capabilities to enhance output visibility during test execution.